Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5381506ea8196559216eab1a28b0f3d4688992e64776feca13f62a50a8cc618

Tx prefix hash: e7718cfd622f5297064ed1fdcb0c5fdf3054cd4c1ec48d8e731fe9426f5dabe7
Tx public key: 86a7a9e9cb4fdd517bc4e2e6663ad16da1e9b158ec303f90077f13d79476af80
Timestamp: 1719722564 Timestamp [UCT]: 2024-06-30 04:42:44 Age [y:d:h:m:s]: 00:262:17:30:22
Block: 1055250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187746 RingCT/type: yes/0
Extra: 0186a7a9e9cb4fdd517bc4e2e6663ad16da1e9b158ec303f90077f13d79476af8002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 373ea7bb8fe2688934696289c3e040e3f34d301b07cc9919d03a82add56ddd86 0.600000000000 1525647 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": 1055260, "vin": [ { "gen": { "height": 1055250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "373ea7bb8fe2688934696289c3e040e3f34d301b07cc9919d03a82add56ddd86" } } ], "extra": [ 1, 134, 167, 169, 233, 203, 79, 221, 81, 123, 196, 226, 230, 102, 58, 209, 109, 161, 233, 177, 88, 236, 48, 63, 144, 7, 127, 19, 215, 148, 118, 175, 128, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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