Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca27fb2b89cba87931e551ae37ab7e6a1e4d2e7ebc57d98e0e0ff0eb1a5b8ba0

Tx prefix hash: 96fd05302145dc576e590dd6b2aec829e37c928e4acacf8de240eb4e623ab8b5
Tx public key: 4a4050ce01b23bfdc35781c1f2ea3a196d549306a0ee3bcd1d3c0c755c50e8e7
Timestamp: 1717730656 Timestamp [UCT]: 2024-06-07 03:24:16 Age [y:d:h:m:s]: 01:011:11:35:03
Block: 1038749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268976 RingCT/type: yes/0
Extra: 014a4050ce01b23bfdc35781c1f2ea3a196d549306a0ee3bcd1d3c0c755c50e8e70211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 644f60f5de9836b94d7668515c8e30927002c8d4c81722991393afbbf9234bba 0.600000000000 1507310 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": 1038759, "vin": [ { "gen": { "height": 1038749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "644f60f5de9836b94d7668515c8e30927002c8d4c81722991393afbbf9234bba" } } ], "extra": [ 1, 74, 64, 80, 206, 1, 178, 59, 253, 195, 87, 129, 193, 242, 234, 58, 25, 109, 84, 147, 6, 160, 238, 59, 205, 29, 60, 12, 117, 92, 80, 232, 231, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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