Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da4ea54d2e2827841c58a0fe7202e886e0dc1fdd8eff4229560d79227e3bfb51

Tx prefix hash: 13a38eebd768cb4c75c2d0e98984387aed0b7ccfc952fcd1d81a87c783ef9445
Tx public key: c14c482f849f175f8b7af550db0e620586faea95724d7ed3f8eca2077dc457de
Timestamp: 1718709754 Timestamp [UCT]: 2024-06-18 11:22:34 Age [y:d:h:m:s]: 00:325:21:39:53
Block: 1046865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232910 RingCT/type: yes/0
Extra: 01c14c482f849f175f8b7af550db0e620586faea95724d7ed3f8eca2077dc457de02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c6ab501fee8eb6755ef7d35461711ca2c11b3f3f938e3b49ac22b800d924226 0.600000000000 1516684 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": 1046875, "vin": [ { "gen": { "height": 1046865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c6ab501fee8eb6755ef7d35461711ca2c11b3f3f938e3b49ac22b800d924226" } } ], "extra": [ 1, 193, 76, 72, 47, 132, 159, 23, 95, 139, 122, 245, 80, 219, 14, 98, 5, 134, 250, 234, 149, 114, 77, 126, 211, 248, 236, 162, 7, 125, 196, 87, 222, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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