Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a547c10b9b658b26152eeda4fdba8d67b98c3b0ae47bd18aef28859e8d9948f

Tx prefix hash: 9315c6d16fbd80bb72b9529808788a3c4f88d8425c6b74543e01e79745f96275
Tx public key: d06c08576abed2b8be814d009618335589b8dc8835bf6186df80d18e27372c7f
Timestamp: 1722897938 Timestamp [UCT]: 2024-08-05 22:45:38 Age [y:d:h:m:s]: 00:141:03:54:38
Block: 1081583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101001 RingCT/type: yes/0
Extra: 01d06c08576abed2b8be814d009618335589b8dc8835bf6186df80d18e27372c7f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f181d9d2bf9e403b063972e22133c3a9857595c7f9bb78c3f83c5b3023f91bef 0.600000000000 1555384 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": 1081593, "vin": [ { "gen": { "height": 1081583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f181d9d2bf9e403b063972e22133c3a9857595c7f9bb78c3f83c5b3023f91bef" } } ], "extra": [ 1, 208, 108, 8, 87, 106, 190, 210, 184, 190, 129, 77, 0, 150, 24, 51, 85, 137, 184, 220, 136, 53, 191, 97, 134, 223, 128, 209, 142, 39, 55, 44, 127, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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