Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 822c71e6548ad3afb85155fb2c60d0bfd17c3b1edc051f2851caf683d5272b12

Tx prefix hash: e1169c721659ef6e641e49d4ce27ec2015fd272b17e5150ace0a91e10ea58d95
Tx public key: 072f834907f1abf76c3c583abdbf40ade1c902e009b30cbf316d2a52c9ca19af
Timestamp: 1714567556 Timestamp [UCT]: 2024-05-01 12:45:56 Age [y:d:h:m:s]: 01:001:05:12:00
Block: 1012520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261797 RingCT/type: yes/0
Extra: 01072f834907f1abf76c3c583abdbf40ade1c902e009b30cbf316d2a52c9ca19af0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3232349164b9236a695964dd47fd12ffb69dea4eb92dc24b854600eee06123a4 0.600000000000 1475074 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": 1012530, "vin": [ { "gen": { "height": 1012520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3232349164b9236a695964dd47fd12ffb69dea4eb92dc24b854600eee06123a4" } } ], "extra": [ 1, 7, 47, 131, 73, 7, 241, 171, 247, 108, 60, 88, 58, 189, 191, 64, 173, 225, 201, 2, 224, 9, 179, 12, 191, 49, 109, 42, 82, 201, 202, 25, 175, 2, 17, 0, 0, 0, 5, 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