Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94ff469908c985541dd4bfc97e607636daf4a6b8da54ad15dcc94aa31df6996e

Tx prefix hash: fa171cfd8ecfd7a3286dd1b70ac1a959b6f82ac6ea222fe22104efd9caaa9f31
Tx public key: 66db1ee5454fbd79f11b5d36a558d02a58d9cc47a41e5cb98a6d44678a3798e4
Timestamp: 1757999463 Timestamp [UCT]: 2025-09-16 05:11:03 Age [y:d:h:m:s]: 00:022:14:47:05
Block: 1369481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16184 RingCT/type: yes/0
Extra: 0166db1ee5454fbd79f11b5d36a558d02a58d9cc47a41e5cb98a6d44678a3798e4021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 639aa4e148cee480d47500aef6d63bae99b9133e7643ccc0efb34eac44e15daf 0.600000000000 1857556 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": 1369491, "vin": [ { "gen": { "height": 1369481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639aa4e148cee480d47500aef6d63bae99b9133e7643ccc0efb34eac44e15daf" } } ], "extra": [ 1, 102, 219, 30, 229, 69, 79, 189, 121, 241, 27, 93, 54, 165, 88, 208, 42, 88, 217, 204, 71, 164, 30, 92, 185, 138, 109, 68, 103, 138, 55, 152, 228, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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