Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ca0c082216d708af42c80cbb88b91706447a54987d8fa672d56d591f608328

Tx prefix hash: 4cc0bd41e92ca55d7d45c1386fb6013c135a8e950c3c11f4b51a888bb37e0899
Tx public key: e06b56f4eaff7fb3bfe411e9e4a67d98c888d4c60841b3c90cf1182c1d37c900
Timestamp: 1760892890 Timestamp [UCT]: 2025-10-19 16:54:50 Age [y:d:h:m:s]: 00:081:02:46:55
Block: 1393478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58072 RingCT/type: yes/0
Extra: 01e06b56f4eaff7fb3bfe411e9e4a67d98c888d4c60841b3c90cf1182c1d37c90002110000000725a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b5be2dc921dd4967026e05aff7b7b79cb071153cc63bb2e6eb2038b709113b 0.600000000000 1881743 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": 1393488, "vin": [ { "gen": { "height": 1393478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b5be2dc921dd4967026e05aff7b7b79cb071153cc63bb2e6eb2038b709113b" } } ], "extra": [ 1, 224, 107, 86, 244, 234, 255, 127, 179, 191, 228, 17, 233, 228, 166, 125, 152, 200, 136, 212, 198, 8, 65, 179, 201, 12, 241, 24, 44, 29, 55, 201, 0, 2, 17, 0, 0, 0, 7, 37, 163, 90, 15, 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