Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa140835033a1e28b0044fc9c9918abda8de4eb9e3f0f88cb3160434a8da86e

Tx prefix hash: 3f8d2b67991d2c005d73bc7128a1f8dea0f9226eaf44b873aeaa349bede1d00b
Tx public key: f4204bfdf1be54945b38982d257771e0979d4d36d4fb6ae1c11d76f8c1511ae3
Timestamp: 1751074336 Timestamp [UCT]: 2025-06-28 01:32:16 Age [y:d:h:m:s]: 00:144:12:40:18
Block: 1314194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101377 RingCT/type: yes/0
Extra: 01f4204bfdf1be54945b38982d257771e0979d4d36d4fb6ae1c11d76f8c1511ae3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b9a5a6f346313cb9869d15cad173910e7e6ddcf6171a72ae9a20ed5c9650e4e 0.600000000000 1801839 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": 1314204, "vin": [ { "gen": { "height": 1314194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9a5a6f346313cb9869d15cad173910e7e6ddcf6171a72ae9a20ed5c9650e4e" } } ], "extra": [ 1, 244, 32, 75, 253, 241, 190, 84, 148, 91, 56, 152, 45, 37, 119, 113, 224, 151, 157, 77, 54, 212, 251, 106, 225, 193, 29, 118, 248, 193, 81, 26, 227, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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