Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55594a43acf496d60cdc06a297995a3fa7610df3e30d1f6f0114950ac75f4757

Tx prefix hash: 27ca72e4098bba0e3c464277b722953a4edc8bfc3b4ef6f8c86e9634fabfc438
Tx public key: 8c29a36c3303cbf44586d1bc6f263be63e87e31d62f8cce5b8fa6f17336ea11f
Timestamp: 1751502943 Timestamp [UCT]: 2025-07-03 00:35:43 Age [y:d:h:m:s]: 00:141:23:45:52
Block: 1317579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99726 RingCT/type: yes/0
Extra: 018c29a36c3303cbf44586d1bc6f263be63e87e31d62f8cce5b8fa6f17336ea11f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5271a3d7d9ffa92d0e16421d07d73e7e81c17ed94d1c26b2fde29de827a0bfa0 0.600000000000 1805248 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": 1317589, "vin": [ { "gen": { "height": 1317579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5271a3d7d9ffa92d0e16421d07d73e7e81c17ed94d1c26b2fde29de827a0bfa0" } } ], "extra": [ 1, 140, 41, 163, 108, 51, 3, 203, 244, 69, 134, 209, 188, 111, 38, 59, 230, 62, 135, 227, 29, 98, 248, 204, 229, 184, 250, 111, 23, 51, 110, 161, 31, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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