Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a7c50bf222857db0d7ff4c482fe6e1a059787e6435ec4b4464653a34b89056

Tx prefix hash: 21de91660e2852f3aebefa087f4d7c8d7a1724581570ecb37797a511a313c3d5
Tx public key: ccc4bbff4b3c6e679d98bcb6fc2652d756e156cc76c9a32d833cf3dcb2ee981f
Timestamp: 1731524193 Timestamp [UCT]: 2024-11-13 18:56:33 Age [y:d:h:m:s]: 00:195:12:43:53
Block: 1153004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139616 RingCT/type: yes/0
Extra: 01ccc4bbff4b3c6e679d98bcb6fc2652d756e156cc76c9a32d833cf3dcb2ee981f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8275e70d573645e3d1648cb285bbff2edc24e9e43ff4118b5a356bed9f34ec2 0.600000000000 1638611 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": 1153014, "vin": [ { "gen": { "height": 1153004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8275e70d573645e3d1648cb285bbff2edc24e9e43ff4118b5a356bed9f34ec2" } } ], "extra": [ 1, 204, 196, 187, 255, 75, 60, 110, 103, 157, 152, 188, 182, 252, 38, 82, 215, 86, 225, 86, 204, 118, 201, 163, 45, 131, 60, 243, 220, 178, 238, 152, 31, 2, 17, 0, 0, 0, 1, 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