Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8872453ee12c86c6676db58ee64c9069261420a622c8ab50c3e12af8d93a146f

Tx prefix hash: f367d8a3c98c904c4a31f7173b791cdbe97254b3b5093bbc7851cc7c1152a368
Tx public key: 98c7805e5bc3b80b569e22343fcdaeaa63f8612b4dc21443ed36ffde1fb89e22
Timestamp: 1712429502 Timestamp [UCT]: 2024-04-06 18:51:42 Age [y:d:h:m:s]: 00:220:15:38:49
Block: 994756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157999 RingCT/type: yes/0
Extra: 0198c7805e5bc3b80b569e22343fcdaeaa63f8612b4dc21443ed36ffde1fb89e220211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee0c5c2cd4a5c039369ccac31db8c5847eb5ae4638f629ad1f14a738e09b116 0.600000000000 1455160 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": 994766, "vin": [ { "gen": { "height": 994756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee0c5c2cd4a5c039369ccac31db8c5847eb5ae4638f629ad1f14a738e09b116" } } ], "extra": [ 1, 152, 199, 128, 94, 91, 195, 184, 11, 86, 158, 34, 52, 63, 205, 174, 170, 99, 248, 97, 43, 77, 194, 20, 67, 237, 54, 255, 222, 31, 184, 158, 34, 2, 17, 0, 0, 0, 1, 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