Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c7574bf8098117f78dbe9e7233da020c2ac98e596c62580ae1ee81821249a6e

Tx prefix hash: 9709df0ae1986763c966fd804134748a911415b479a33419c1db55795dba5fc1
Tx public key: b7f2d68dd0e6459f1010a9e1ecf29eb10640112a9377f355ec944515cf2be5d4
Timestamp: 1701979354 Timestamp [UCT]: 2023-12-07 20:02:34 Age [y:d:h:m:s]: 01:103:10:52:04
Block: 908155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335091 RingCT/type: yes/0
Extra: 01b7f2d68dd0e6459f1010a9e1ecf29eb10640112a9377f355ec944515cf2be5d402110000000139e1d5d3000000000000000000

1 output(s) for total of 0.601042889000 dcy

stealth address amount amount idx
00: bf7e6a567c11d4b22a9a330e05d63d29a5108c6236006a6f5c120ad3f35002db 0.601042889000 1365180 of 0

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": 908165, "vin": [ { "gen": { "height": 908155 } } ], "vout": [ { "amount": 601042889, "target": { "key": "bf7e6a567c11d4b22a9a330e05d63d29a5108c6236006a6f5c120ad3f35002db" } } ], "extra": [ 1, 183, 242, 214, 141, 208, 230, 69, 159, 16, 16, 169, 225, 236, 242, 158, 177, 6, 64, 17, 42, 147, 119, 243, 85, 236, 148, 69, 21, 207, 43, 229, 212, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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