Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47de2f5774be5ba0263b47d085d4028a5560cb7c70b9636502ac408c107ac991

Tx prefix hash: b80246a48f345c060536e334a02f1c0f00ae90d39d7a3faef7460d76bbc178de
Tx public key: 5dceb00e0f66ed409b1008d096d5cad8ae96272b2649e127f59d60d56dda8456
Timestamp: 1707748146 Timestamp [UCT]: 2024-02-12 14:29:06 Age [y:d:h:m:s]: 01:015:18:43:01
Block: 955970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272300 RingCT/type: yes/0
Extra: 015dceb00e0f66ed409b1008d096d5cad8ae96272b2649e127f59d60d56dda8456021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c4cdca6ac9054dd9d5e8f4a4dbcbd4ee0619c52245b97a7e297d047cc3766fa 0.600000000000 1415272 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": 955980, "vin": [ { "gen": { "height": 955970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c4cdca6ac9054dd9d5e8f4a4dbcbd4ee0619c52245b97a7e297d047cc3766fa" } } ], "extra": [ 1, 93, 206, 176, 14, 15, 102, 237, 64, 155, 16, 8, 208, 150, 213, 202, 216, 174, 150, 39, 43, 38, 73, 225, 39, 245, 157, 96, 213, 109, 218, 132, 86, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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