Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e9f153e61c1049267e7acfb8d3d6f766b14358c84a6c4a7c66ce5fd0fe8ab38

Tx prefix hash: 2e99002f6a83e60369fd778f31b42cdd8631d2f1cbab2f9ea5b737b29c061d54
Tx public key: 6713babc8a7630966dce876c0d63f47e156533c5377d05f8aabcca2c2d22430e
Timestamp: 1737958807 Timestamp [UCT]: 2025-01-27 06:20:07 Age [y:d:h:m:s]: 00:324:01:26:24
Block: 1206053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229366 RingCT/type: yes/0
Extra: 016713babc8a7630966dce876c0d63f47e156533c5377d05f8aabcca2c2d22430e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 797b2b3ffaffac3f5d7a0e9b65d6fd43e44a2b7d5096929c39f5d676e956cea7 0.600000000000 1692754 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": 1206063, "vin": [ { "gen": { "height": 1206053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "797b2b3ffaffac3f5d7a0e9b65d6fd43e44a2b7d5096929c39f5d676e956cea7" } } ], "extra": [ 1, 103, 19, 186, 188, 138, 118, 48, 150, 109, 206, 135, 108, 13, 99, 244, 126, 21, 101, 51, 197, 55, 125, 5, 248, 170, 188, 202, 44, 45, 34, 67, 14, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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