Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae9b98215141cc5733e7a6f7138a91eef7ef8c06f3b800bc3018003e7880a82

Tx prefix hash: 1b6d6f5ac656669cb9256c3bffd7406c5df46bd36cd1609c51a4c799ceb7ebd3
Tx public key: 36af0b0b787f444483d2cea208ce5287fd305bd34e986915fa6f5c4e2d5d4fab
Timestamp: 1735444090 Timestamp [UCT]: 2024-12-29 03:48:10 Age [y:d:h:m:s]: 00:099:10:10:01
Block: 1185466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70847 RingCT/type: yes/0
Extra: 0136af0b0b787f444483d2cea208ce5287fd305bd34e986915fa6f5c4e2d5d4fab021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aea8eabdb0ff249db43a3f68ef2a74f6399c836b9993482555e3d4f2288cfcc 0.600000000000 1671937 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": 1185476, "vin": [ { "gen": { "height": 1185466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aea8eabdb0ff249db43a3f68ef2a74f6399c836b9993482555e3d4f2288cfcc" } } ], "extra": [ 1, 54, 175, 11, 11, 120, 127, 68, 68, 131, 210, 206, 162, 8, 206, 82, 135, 253, 48, 91, 211, 78, 152, 105, 21, 250, 111, 92, 78, 45, 93, 79, 171, 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