Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b104a5873159c1a808cc18f7d3141040c37c0c1b6cebfe70139c813d1b954706

Tx prefix hash: 48b16cbcda207e3d2a26c9a641a83d1f3cf9e2b15500de3cbf029bd3c895e0d6
Tx public key: 21ccb266d479a95dfe07ec297e8a98fa3ad15d34a9633177167cd2fae0e197bf
Timestamp: 1684942371 Timestamp [UCT]: 2023-05-24 15:32:51 Age [y:d:h:m:s]: 02:167:16:02:43
Block: 767165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639621 RingCT/type: yes/0
Extra: 0121ccb266d479a95dfe07ec297e8a98fa3ad15d34a9633177167cd2fae0e197bf02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.762235994000 dcy

stealth address amount amount idx
00: a6abae9277ca7dd8f818fc2d97ecd633b895d6d0f52506ca07106e450266852b 1.762235994000 1216270 of 0

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": 767175, "vin": [ { "gen": { "height": 767165 } } ], "vout": [ { "amount": 1762235994, "target": { "key": "a6abae9277ca7dd8f818fc2d97ecd633b895d6d0f52506ca07106e450266852b" } } ], "extra": [ 1, 33, 204, 178, 102, 212, 121, 169, 93, 254, 7, 236, 41, 126, 138, 152, 250, 58, 209, 93, 52, 169, 99, 49, 119, 22, 124, 210, 250, 224, 225, 151, 191, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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