Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c90455ef1918c353acc1192ddf06966a1b13623413c6216d14836b507f0460d

Tx prefix hash: 13fe51883fdfab76fe9cb0757abd1ccffa7fad4d79b0e6e437bbff2492b753f5
Tx public key: e33ea4f6cee3e24cbbac0a2c89db5df67fae8037b8719022290a4494c6d8a8c3
Timestamp: 1702367570 Timestamp [UCT]: 2023-12-12 07:52:50 Age [y:d:h:m:s]: 01:045:13:17:30
Block: 911383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293874 RingCT/type: yes/0
Extra: 01e33ea4f6cee3e24cbbac0a2c89db5df67fae8037b8719022290a4494c6d8a8c302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe0c3ceeeb8b26af1cf946c7c5f2012f1cbd5f63f8d7f5301b9ea5bc0efedbe2 0.600000000000 1368583 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": 911393, "vin": [ { "gen": { "height": 911383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0c3ceeeb8b26af1cf946c7c5f2012f1cbd5f63f8d7f5301b9ea5bc0efedbe2" } } ], "extra": [ 1, 227, 62, 164, 246, 206, 227, 226, 76, 187, 172, 10, 44, 137, 219, 93, 246, 127, 174, 128, 55, 184, 113, 144, 34, 41, 10, 68, 148, 198, 216, 168, 195, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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