Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6ce9341732fd17d93ef392f4b9a9775d25f5dc9133f91f86747bc6dae4f6a6

Tx prefix hash: 0aefb3a22ad23943a79714a6a3285626a72c73ae60f3b51ba07ddde632b8ea86
Tx public key: a7cb44d7e06af0582cbe957113848184cde9b0ad77e9298254abfbb074c14646
Timestamp: 1715279078 Timestamp [UCT]: 2024-05-09 18:24:38 Age [y:d:h:m:s]: 00:336:23:44:57
Block: 1018418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240880 RingCT/type: yes/0
Extra: 01a7cb44d7e06af0582cbe957113848184cde9b0ad77e9298254abfbb074c1464602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b88f958726cfc13b18c2fdde3dff22457f8c5af64db1867125f564f251a4f33f 0.600000000000 1482207 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": 1018428, "vin": [ { "gen": { "height": 1018418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b88f958726cfc13b18c2fdde3dff22457f8c5af64db1867125f564f251a4f33f" } } ], "extra": [ 1, 167, 203, 68, 215, 224, 106, 240, 88, 44, 190, 149, 113, 19, 132, 129, 132, 205, 233, 176, 173, 119, 233, 41, 130, 84, 171, 251, 176, 116, 193, 70, 70, 2, 17, 0, 0, 0, 1, 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