Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bb155e2a51f94c0cf4c744832c233d85f979976a45dcb364954d178da746cdd

Tx prefix hash: f27aa5dd158039a18e586ff2fbbe7174adb6d39da4cf84e4a629d1a4c5cff7b7
Tx public key: 9f225712428999d9b78ad7e78e73c76923f8dfaceb0addd3ef8ae5f06caefb46
Timestamp: 1747915213 Timestamp [UCT]: 2025-05-22 12:00:13 Age [y:d:h:m:s]: 00:182:21:40:00
Block: 1288454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128406 RingCT/type: yes/0
Extra: 019f225712428999d9b78ad7e78e73c76923f8dfaceb0addd3ef8ae5f06caefb4602110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8877bc492758e6fd75dfa73bf1e2bd3bc1a5ecd2567d38a64c78a0b7f754d492 0.600000000000 1775921 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": 1288464, "vin": [ { "gen": { "height": 1288454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8877bc492758e6fd75dfa73bf1e2bd3bc1a5ecd2567d38a64c78a0b7f754d492" } } ], "extra": [ 1, 159, 34, 87, 18, 66, 137, 153, 217, 183, 138, 215, 231, 142, 115, 199, 105, 35, 248, 223, 172, 235, 10, 221, 211, 239, 138, 229, 240, 108, 174, 251, 70, 2, 17, 0, 0, 0, 2, 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