Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e672df67320844874ee171ad0cc8b41d9346c0f43e4b02206f3996e0f7fa75

Tx prefix hash: 971117b29a099464341faaa10db01b884d96c092a48399c90d52f4c1cdc3bb72
Tx public key: 1c2319d1cf903be0904eec3d6c9cc55c1ac2a4fc11a488d6699a15fde4fab65d
Timestamp: 1709521343 Timestamp [UCT]: 2024-03-04 03:02:23 Age [y:d:h:m:s]: 01:074:04:54:28
Block: 970687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314061 RingCT/type: yes/0
Extra: 011c2319d1cf903be0904eec3d6c9cc55c1ac2a4fc11a488d6699a15fde4fab65d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2174c1544ba1f099be1373c1e38228ca05d534321abf2840f2726018016ad4 0.600000000000 1430546 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": 970697, "vin": [ { "gen": { "height": 970687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2174c1544ba1f099be1373c1e38228ca05d534321abf2840f2726018016ad4" } } ], "extra": [ 1, 28, 35, 25, 209, 207, 144, 59, 224, 144, 78, 236, 61, 108, 156, 197, 92, 26, 194, 164, 252, 17, 164, 136, 214, 105, 154, 21, 253, 228, 250, 182, 93, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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