Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8d0cd236e0c3da1fa382887afa7185f88d9f55328e4557d0a4c318a46c519a5a

Tx prefix hash: 1e54629027e4f2231f6cd7b04e8277e4672bc770ed79b81329f3219fb755fb88
Tx public key: 2a7ec758e848010bdfb1fcf5882f976f2efc5008d42ec6e164134679026545e7
Timestamp: 1709634733 Timestamp [UCT]: 2024-03-05 10:32:13 Age [y:d:h:m:s]: 01:034:20:31:07
Block: 971630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285907 RingCT/type: yes/0
Extra: 012a7ec758e848010bdfb1fcf5882f976f2efc5008d42ec6e164134679026545e702110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf0c6074b013eab95e73dcc6e055c62bc4fbd248fe2f27318a8253dd6d4d7b8 0.600000000000 1431527 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 971640, "vin": [ { "gen": { "height": 971630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf0c6074b013eab95e73dcc6e055c62bc4fbd248fe2f27318a8253dd6d4d7b8" } } ], "extra": [ 1, 42, 126, 199, 88, 232, 72, 1, 11, 223, 177, 252, 245, 136, 47, 151, 111, 46, 252, 80, 8, 212, 46, 198, 225, 100, 19, 70, 121, 2, 101, 69, 231, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8