Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fc52b498b6baf941b08a82db7c59242f9339fc12d69754d86bcad525a70333c

Tx prefix hash: 07ceda00057ddf625906c9ba370c942996bd3021c7a8243112c8312672866d7c
Tx public key: 6ecc9a811e9ad4aed21311789e556ee1b1bb940b6a1418e3f774828efb21cf9e
Timestamp: 1724099757 Timestamp [UCT]: 2024-08-19 20:35:57 Age [y:d:h:m:s]: 00:222:00:30:59
Block: 1091547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158545 RingCT/type: yes/0
Extra: 016ecc9a811e9ad4aed21311789e556ee1b1bb940b6a1418e3f774828efb21cf9e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57d3f821c41fdee396e066abc87eec9ff976f7da9e963e03e4c10c66ca1a25f3 0.600000000000 1566180 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": 1091557, "vin": [ { "gen": { "height": 1091547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57d3f821c41fdee396e066abc87eec9ff976f7da9e963e03e4c10c66ca1a25f3" } } ], "extra": [ 1, 110, 204, 154, 129, 30, 154, 212, 174, 210, 19, 17, 120, 158, 85, 110, 225, 177, 187, 148, 11, 106, 20, 24, 227, 247, 116, 130, 142, 251, 33, 207, 158, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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