Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4470e893a28c64777ed99b1e95e9f336b27f3810e58b8a6cfbb83c44084f555d

Tx prefix hash: ce5f0e7d12834289d00c4cb188ac62ee219c69344d52bdad5d474e06ff88e30b
Tx public key: 1ba8c35586676e56234e8236db06ff2ff9bb1e3f0778e82dd3d3b78c0075c7b9
Timestamp: 1751749642 Timestamp [UCT]: 2025-07-05 21:07:22 Age [y:d:h:m:s]: 00:136:02:04:12
Block: 1319492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95631 RingCT/type: yes/0
Extra: 011ba8c35586676e56234e8236db06ff2ff9bb1e3f0778e82dd3d3b78c0075c7b902110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f967e9864ba5f805898e2a119609d3bec6ee3a0f8c8cb47d6a5ed720c9eafbc 0.600000000000 1807185 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": 1319502, "vin": [ { "gen": { "height": 1319492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f967e9864ba5f805898e2a119609d3bec6ee3a0f8c8cb47d6a5ed720c9eafbc" } } ], "extra": [ 1, 27, 168, 195, 85, 134, 103, 110, 86, 35, 78, 130, 54, 219, 6, 255, 47, 249, 187, 30, 63, 7, 120, 232, 45, 211, 211, 183, 140, 0, 117, 199, 185, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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