Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c19d965a0cff925d0337828c869029455d7eeb027e02a95d3d37a2d27640e271

Tx prefix hash: 704bdd7b547dac4849c8a3a2b7b82b5618da7431b2e851dc5cc61d8e38adc9c4
Tx public key: d76293c2ef77285d4bf9f5394288231ec71005a3b695c283d50920461f0a5d3f
Timestamp: 1698967588 Timestamp [UCT]: 2023-11-02 23:26:28 Age [y:d:h:m:s]: 01:192:18:22:37
Block: 883394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398797 RingCT/type: yes/0
Extra: 01d76293c2ef77285d4bf9f5394288231ec71005a3b695c283d50920461f0a5d3f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.726020647000 dcy

stealth address amount amount idx
00: ff751b853e6de1b7871ae2aea8fa8852b13a5a340f4ecee4a5e3ea948694581e 0.726020647000 1339090 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": 883404, "vin": [ { "gen": { "height": 883394 } } ], "vout": [ { "amount": 726020647, "target": { "key": "ff751b853e6de1b7871ae2aea8fa8852b13a5a340f4ecee4a5e3ea948694581e" } } ], "extra": [ 1, 215, 98, 147, 194, 239, 119, 40, 93, 75, 249, 245, 57, 66, 136, 35, 30, 199, 16, 5, 163, 182, 149, 194, 131, 213, 9, 32, 70, 31, 10, 93, 63, 2, 17, 0, 0, 0, 3, 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