Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b9cb219d3cb3b36fbe018b50ff71796836196449170ab7bfced61377b0c76d

Tx prefix hash: 2a6e8f24bd19ac12a146f91b32472076df5a845678184e908e39fea1e815d83a
Tx public key: 16d921b423322a9e090fc31704c67e48c27916e5d5d05afa0b220d793c63566b
Timestamp: 1730910742 Timestamp [UCT]: 2024-11-06 16:32:22 Age [y:d:h:m:s]: 00:000:20:45:49
Block: 1147925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623 RingCT/type: yes/0
Extra: 0116d921b423322a9e090fc31704c67e48c27916e5d5d05afa0b220d793c63566b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a04179b9c5332dea7a21e33d616b4a21d10e755222f20d4a4d7094f1c94ac71 0.600000000000 1632640 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": 1147935, "vin": [ { "gen": { "height": 1147925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a04179b9c5332dea7a21e33d616b4a21d10e755222f20d4a4d7094f1c94ac71" } } ], "extra": [ 1, 22, 217, 33, 180, 35, 50, 42, 158, 9, 15, 195, 23, 4, 198, 126, 72, 194, 121, 22, 229, 213, 208, 90, 250, 11, 34, 13, 121, 60, 99, 86, 107, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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