Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64268b2910db84f75a7dc1517c3ce9122f2dac65de135bb6341b3e17830033b

Tx prefix hash: 579da1fdebfe6ee31a7a41b0ea727a453d226f1a0b8240e7adc5f9c555f9326b
Tx public key: 14395bb6762baf126d178b94e13a32c5fee796b375fd9b096b6a02ae00e5a900
Timestamp: 1734235210 Timestamp [UCT]: 2024-12-15 04:00:10 Age [y:d:h:m:s]: 00:134:04:38:32
Block: 1175481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95701 RingCT/type: yes/0
Extra: 0114395bb6762baf126d178b94e13a32c5fee796b375fd9b096b6a02ae00e5a900021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2db838f2ed593e30703c992c756a0126ff97415acc4b7ae414ca288664d72843 0.600000000000 1661766 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": 1175491, "vin": [ { "gen": { "height": 1175481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2db838f2ed593e30703c992c756a0126ff97415acc4b7ae414ca288664d72843" } } ], "extra": [ 1, 20, 57, 91, 182, 118, 43, 175, 18, 109, 23, 139, 148, 225, 58, 50, 197, 254, 231, 150, 179, 117, 253, 155, 9, 107, 106, 2, 174, 0, 229, 169, 0, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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