Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c86258e4c47e1b73b953237a10e1a86c1db90f3bc39c78156975ce6124070bde

Tx prefix hash: e842b1876ce2b43251b61d1f93cee4b6f31002bb190783ff15fd0efe1301513a
Tx public key: 908804d6c8c0db992cc30a2d8b8a6e0e42f7a85ef62851e20ab8d250bd7886ca
Timestamp: 1755860991 Timestamp [UCT]: 2025-08-22 11:09:51 Age [y:d:h:m:s]: 00:039:08:23:27
Block: 1351940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27980 RingCT/type: yes/0
Extra: 01908804d6c8c0db992cc30a2d8b8a6e0e42f7a85ef62851e20ab8d250bd7886ca0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84ade31be700d6dd2f6c9e804bcc76a309b9e64cfafeb7627b79298db616e002 0.600000000000 1839901 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": 1351950, "vin": [ { "gen": { "height": 1351940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84ade31be700d6dd2f6c9e804bcc76a309b9e64cfafeb7627b79298db616e002" } } ], "extra": [ 1, 144, 136, 4, 214, 200, 192, 219, 153, 44, 195, 10, 45, 139, 138, 110, 14, 66, 247, 168, 94, 246, 40, 81, 226, 10, 184, 210, 80, 189, 120, 134, 202, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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