Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9fe2d047d548050f6d49ddb64e01736d4c85c7bfebd3b76dc2fbd861c9aae7

Tx prefix hash: bd1778ec2f762516c3b149b1a9c5fc25a280e6471db755c097d30f8a241eb8a0
Tx public key: 87ef2cf7cb5517055c60dd3178efa9866cb77395ef0b88f2c1e087b352a94e01
Timestamp: 1656976775 Timestamp [UCT]: 2022-07-04 23:19:35 Age [y:d:h:m:s]: 02:185:04:56:27
Block: 536756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653741 RingCT/type: yes/0
Extra: 0187ef2cf7cb5517055c60dd3178efa9866cb77395ef0b88f2c1e087b352a94e01021100000002d3fcec30000000000000000000

1 output(s) for total of 10.221266355000 dcy

stealth address amount amount idx
00: 42fa32b0d53e397ae6433efd62ff6f5ea410b2623763b5e169f598b1d33d4fe8 10.221266355000 966555 of 0

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": 536766, "vin": [ { "gen": { "height": 536756 } } ], "vout": [ { "amount": 10221266355, "target": { "key": "42fa32b0d53e397ae6433efd62ff6f5ea410b2623763b5e169f598b1d33d4fe8" } } ], "extra": [ 1, 135, 239, 44, 247, 203, 85, 23, 5, 92, 96, 221, 49, 120, 239, 169, 134, 108, 183, 115, 149, 239, 11, 136, 242, 193, 224, 135, 179, 82, 169, 78, 1, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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