Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d98074ad671d4e47c5cd4721bb540a7ab1bdb362b90fff47171e4708461af79

Tx prefix hash: 1e94b44e94e7af43ab1c31650f8db8a1dc704b06b89355d8d9d2c34dccc5b0f6
Tx public key: 6628b00579a007fcacbe4851b76c3c6715fc6697c4a9982b0193910fbf380c95
Timestamp: 1703227219 Timestamp [UCT]: 2023-12-22 06:40:19 Age [y:d:h:m:s]: 01:323:00:42:32
Block: 918497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489711 RingCT/type: yes/0
Extra: 016628b00579a007fcacbe4851b76c3c6715fc6697c4a9982b0193910fbf380c9502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f421cf09dc4639b52e0405a197afd263c627823a18bea97b0bc5f1c7f94b3c1a 0.600000000000 1376141 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": 918507, "vin": [ { "gen": { "height": 918497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f421cf09dc4639b52e0405a197afd263c627823a18bea97b0bc5f1c7f94b3c1a" } } ], "extra": [ 1, 102, 40, 176, 5, 121, 160, 7, 252, 172, 190, 72, 81, 183, 108, 60, 103, 21, 252, 102, 151, 196, 169, 152, 43, 1, 147, 145, 15, 191, 56, 12, 149, 2, 17, 0, 0, 0, 7, 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