Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87d11f3865e9d7d6bd61b4034d10852b14a37c4f4170566a57e3abeeb974b460

Tx prefix hash: 3f2614e17bc602267ab08757b14cd276f172b88c00dcd5608b6970cd128f2e46
Tx public key: 13dc4a29cf3c79d6a4b2452ec740dc9b521b876236a39a7800640169957a5f31
Timestamp: 1722318722 Timestamp [UCT]: 2024-07-30 05:52:02 Age [y:d:h:m:s]: 00:238:18:27:30
Block: 1076781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170531 RingCT/type: yes/0
Extra: 0113dc4a29cf3c79d6a4b2452ec740dc9b521b876236a39a7800640169957a5f3102110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f266d0a81bbf65ea1568989e3c9b3545c870a57aadb6bb728b871deaec28e451 0.600000000000 1549322 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": 1076791, "vin": [ { "gen": { "height": 1076781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f266d0a81bbf65ea1568989e3c9b3545c870a57aadb6bb728b871deaec28e451" } } ], "extra": [ 1, 19, 220, 74, 41, 207, 60, 121, 214, 164, 178, 69, 46, 199, 64, 220, 155, 82, 27, 135, 98, 54, 163, 154, 120, 0, 100, 1, 105, 149, 122, 95, 49, 2, 17, 0, 0, 0, 15, 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