Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cf2a9628cf4bc91b6d08dd1fb00a61a58998359856a3a2fe72a9f1daf216e8

Tx prefix hash: df349efbe505fab8c6671370ea0a42f63f2e9ed1296addb2702d4676a9c065f2
Tx public key: 901a43def41fe1620a562341002be0d8e91c0ec82f51971a07a42785a73646fd
Timestamp: 1733329592 Timestamp [UCT]: 2024-12-04 16:26:32 Age [y:d:h:m:s]: 00:109:20:54:59
Block: 1167957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78322 RingCT/type: yes/0
Extra: 01901a43def41fe1620a562341002be0d8e91c0ec82f51971a07a42785a73646fd0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bc71add48ad9e2c225e8ede5a566eb422c5c29f66cea63c16b2e8e382dfe3d4 0.600000000000 1653662 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": 1167967, "vin": [ { "gen": { "height": 1167957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bc71add48ad9e2c225e8ede5a566eb422c5c29f66cea63c16b2e8e382dfe3d4" } } ], "extra": [ 1, 144, 26, 67, 222, 244, 31, 225, 98, 10, 86, 35, 65, 0, 43, 224, 216, 233, 28, 14, 200, 47, 81, 151, 26, 7, 164, 39, 133, 167, 54, 70, 253, 2, 17, 0, 0, 0, 5, 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