Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324e155f106159b5f34035d84a255083ed97fab034db989c339f00d2362274b0

Tx prefix hash: 092f33409564a6b4948d0e4adf30ee65bb3e0856f6ce4545d19d8e9b4422ebe8
Tx public key: f121ab2b0bf815415e5d5b91cc64ca4e37c9b570745fafc8d8d066188d52fac4
Timestamp: 1705006139 Timestamp [UCT]: 2024-01-11 20:48:59 Age [y:d:h:m:s]: 01:117:12:26:12
Block: 933230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345119 RingCT/type: yes/0
Extra: 01f121ab2b0bf815415e5d5b91cc64ca4e37c9b570745fafc8d8d066188d52fac402110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d6f774f131d5a79af7ab20fd71a39fdb6978c39e3a18ec4fa54fb7531e804d1 0.600000000000 1391190 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": 933240, "vin": [ { "gen": { "height": 933230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d6f774f131d5a79af7ab20fd71a39fdb6978c39e3a18ec4fa54fb7531e804d1" } } ], "extra": [ 1, 241, 33, 171, 43, 11, 248, 21, 65, 94, 93, 91, 145, 204, 100, 202, 78, 55, 201, 181, 112, 116, 95, 175, 200, 216, 208, 102, 24, 141, 82, 250, 196, 2, 17, 0, 0, 0, 15, 122, 156, 244, 199, 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