Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6573b2d2af77e5787f62589a958ab8e8078087ec290e98655a2b58385a61df

Tx prefix hash: b86396938f963f6248e1b4ac3b086bdf5d5d0ee19dfc8332cafc49913c69b502
Tx public key: e4f075c406e7adae48072d38e65c8fa8a3dfcf2e6bc35199094e5d48bcc0ebbf
Timestamp: 1710802562 Timestamp [UCT]: 2024-03-18 22:56:02 Age [y:d:h:m:s]: 01:015:19:46:56
Block: 981324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272263 RingCT/type: yes/0
Extra: 01e4f075c406e7adae48072d38e65c8fa8a3dfcf2e6bc35199094e5d48bcc0ebbf02110000001352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1c57211f08db7d412c3035592f142529ed06146162561e26b2a627135c7ab2 0.600000000000 1441419 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": 981334, "vin": [ { "gen": { "height": 981324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1c57211f08db7d412c3035592f142529ed06146162561e26b2a627135c7ab2" } } ], "extra": [ 1, 228, 240, 117, 196, 6, 231, 173, 174, 72, 7, 45, 56, 230, 92, 143, 168, 163, 223, 207, 46, 107, 195, 81, 153, 9, 78, 93, 72, 188, 192, 235, 191, 2, 17, 0, 0, 0, 19, 82, 212, 126, 148, 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