Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 112fd06ab49482ac1cc21f3316b02519bf541b1b6abbd5b7450e63e148e95b86

Tx prefix hash: 26053233273adb1cc2f6663283fca6b495f8d34040bc962b3d9fe926e8ae3f8a
Tx public key: e975efeaee18b6add467a872f714f3acd10fb5a0ce552f5f6e3802d0194dde39
Timestamp: 1735813510 Timestamp [UCT]: 2025-01-02 10:25:10 Age [y:d:h:m:s]: 00:163:08:15:49
Block: 1188527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116491 RingCT/type: yes/0
Extra: 01e975efeaee18b6add467a872f714f3acd10fb5a0ce552f5f6e3802d0194dde39021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b02d102a939be7f8efbc8aff43489ba518a6417060663645b9fbf9c6bbf4d8f7 0.600000000000 1675028 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": 1188537, "vin": [ { "gen": { "height": 1188527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b02d102a939be7f8efbc8aff43489ba518a6417060663645b9fbf9c6bbf4d8f7" } } ], "extra": [ 1, 233, 117, 239, 234, 238, 24, 182, 173, 212, 103, 168, 114, 247, 20, 243, 172, 209, 15, 181, 160, 206, 85, 47, 95, 110, 56, 2, 208, 25, 77, 222, 57, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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