Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8754a62dfba63af37c398fd2a0c80f0bc7c89fd187e5d401833055d876e88a83

Tx prefix hash: 5c80f7a5e783e61e232708461d2a31e467af3b647004805152de8bd11228a3d4
Tx public key: 6f8e577b7ed7ff3f138c5a816930c3582f3143348d54dc09da9f2853bd52be48
Timestamp: 1706635886 Timestamp [UCT]: 2024-01-30 17:31:26 Age [y:d:h:m:s]: 00:360:05:20:28
Block: 946741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257848 RingCT/type: yes/0
Extra: 016f8e577b7ed7ff3f138c5a816930c3582f3143348d54dc09da9f2853bd52be480211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3d3adc01fa9d735331235d4ecbae6a6b1c295fbe818e7163a14f827af0db2b4 0.600000000000 1405081 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": 946751, "vin": [ { "gen": { "height": 946741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3d3adc01fa9d735331235d4ecbae6a6b1c295fbe818e7163a14f827af0db2b4" } } ], "extra": [ 1, 111, 142, 87, 123, 126, 215, 255, 63, 19, 140, 90, 129, 105, 48, 195, 88, 47, 49, 67, 52, 141, 84, 220, 9, 218, 159, 40, 83, 189, 82, 190, 72, 2, 17, 0, 0, 0, 1, 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