Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed26dc85ef753d51c089dab87253b99fb484ab53427aef626d15da8755b4dc7c

Tx prefix hash: 02b743df632d74bb950c87f7130b3cc1b3570ca50e16d39043ce91b8a899f48f
Tx public key: f2c2b2ad20faebb732baaa809c14e8b055ada6ff6487ea8fd8208247d27ca98a
Timestamp: 1744409944 Timestamp [UCT]: 2025-04-11 22:19:04 Age [y:d:h:m:s]: 00:270:15:21:06
Block: 1259431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191218 RingCT/type: yes/0
Extra: 01f2c2b2ad20faebb732baaa809c14e8b055ada6ff6487ea8fd8208247d27ca98a02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb0769dfd354ff419a13aabbc5c5fcd5a9c1ed534c324fb85c364bab543f915 0.600000000000 1746570 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": 1259441, "vin": [ { "gen": { "height": 1259431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb0769dfd354ff419a13aabbc5c5fcd5a9c1ed534c324fb85c364bab543f915" } } ], "extra": [ 1, 242, 194, 178, 173, 32, 250, 235, 183, 50, 186, 170, 128, 156, 20, 232, 176, 85, 173, 166, 255, 100, 135, 234, 143, 216, 32, 130, 71, 210, 124, 169, 138, 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