Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7254556f41e3d80c79ebc42ecb4e5fb0c0a52d410f8f4d063717d387bf1b526d

Tx prefix hash: f9f3960a5edf7acd66d69d759034fc094d341fdb4d0778ffbb8bf4768cfff49a
Tx public key: 7f689f08b199148b5478f1c6684af2a314c4a169749fbbbbb319e27f452043e6
Timestamp: 1712940152 Timestamp [UCT]: 2024-04-12 16:42:32 Age [y:d:h:m:s]: 01:201:09:05:17
Block: 999007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402609 RingCT/type: yes/0
Extra: 017f689f08b199148b5478f1c6684af2a314c4a169749fbbbbb319e27f452043e60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd3e728bfd73a6521445972b571ded1332c7a562ee9ed488512fb0963368eeed 0.600000000000 1459483 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": 999017, "vin": [ { "gen": { "height": 999007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd3e728bfd73a6521445972b571ded1332c7a562ee9ed488512fb0963368eeed" } } ], "extra": [ 1, 127, 104, 159, 8, 177, 153, 20, 139, 84, 120, 241, 198, 104, 74, 242, 163, 20, 196, 161, 105, 116, 159, 187, 187, 179, 25, 226, 127, 69, 32, 67, 230, 2, 17, 0, 0, 0, 1, 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