Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df01081a6cc1ed231e5fecc8b8b56579a2a9fe4347c01073b47f9b23006bd7f3

Tx prefix hash: 05aae8f65b56ecac247c3d20fa4bc4421f0ca9d89f8dbbe6574847eb5a2e740c
Tx public key: d2c3cbd571ef81404fee1d6455f13cb6dcbeb8fe73075ea47bf2f7e169e57f2c
Timestamp: 1703378645 Timestamp [UCT]: 2023-12-24 00:44:05 Age [y:d:h:m:s]: 01:164:16:31:14
Block: 919755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378887 RingCT/type: yes/0
Extra: 01d2c3cbd571ef81404fee1d6455f13cb6dcbeb8fe73075ea47bf2f7e169e57f2c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bec4372102036f4413abb197412f0157f8d204891e7d2d49a2b1fa813da2516 0.600000000000 1377433 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": 919765, "vin": [ { "gen": { "height": 919755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bec4372102036f4413abb197412f0157f8d204891e7d2d49a2b1fa813da2516" } } ], "extra": [ 1, 210, 195, 203, 213, 113, 239, 129, 64, 79, 238, 29, 100, 85, 241, 60, 182, 220, 190, 184, 254, 115, 7, 94, 164, 123, 242, 247, 225, 105, 229, 127, 44, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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