Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e39238e420d59cfd16d92762009901cc05f3d026d7a74ce118e67df05403f1

Tx prefix hash: 5971bce08c0e6bb71603a68269f9514ce66c6949790fdd1da41e7f4a8d2fc8d6
Tx public key: 4ec70a54a550a135c06429bf19142c03f2aaad6ab3e360d229d5b7e07e8b8059
Timestamp: 1733691239 Timestamp [UCT]: 2024-12-08 20:53:59 Age [y:d:h:m:s]: 00:109:10:00:00
Block: 1170979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77967 RingCT/type: yes/0
Extra: 014ec70a54a550a135c06429bf19142c03f2aaad6ab3e360d229d5b7e07e8b8059021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0659791d5b3be1076a440bc0f46d26a3d9b3a2ffa16f31e61a77d093a455fd 0.600000000000 1656714 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": 1170989, "vin": [ { "gen": { "height": 1170979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0659791d5b3be1076a440bc0f46d26a3d9b3a2ffa16f31e61a77d093a455fd" } } ], "extra": [ 1, 78, 199, 10, 84, 165, 80, 161, 53, 192, 100, 41, 191, 25, 20, 44, 3, 242, 170, 173, 106, 179, 227, 96, 210, 41, 213, 183, 224, 126, 139, 128, 89, 2, 17, 0, 0, 0, 5, 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