Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0bd7d10026c4efa7d99b3ee6094b291e5e4c78931c80e2da6da9fbb168e94d

Tx prefix hash: aafa811437ab1a6cf1eba3ac1415232bbeaa609b1d9745a740ff84d352e06e79
Tx public key: e768a574795c46536c925d1ebf81e4471d6b7147cee4a4f772293323d9f8a5f5
Timestamp: 1721770326 Timestamp [UCT]: 2024-07-23 21:32:06 Age [y:d:h:m:s]: 00:250:22:55:44
Block: 1072226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179276 RingCT/type: yes/0
Extra: 01e768a574795c46536c925d1ebf81e4471d6b7147cee4a4f772293323d9f8a5f5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a8b683ebfd0199796633175c0614b25ea74e82f81600fb0424bdc17227b8ac4 0.600000000000 1544683 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": 1072236, "vin": [ { "gen": { "height": 1072226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a8b683ebfd0199796633175c0614b25ea74e82f81600fb0424bdc17227b8ac4" } } ], "extra": [ 1, 231, 104, 165, 116, 121, 92, 70, 83, 108, 146, 93, 30, 191, 129, 228, 71, 29, 107, 113, 71, 206, 228, 164, 247, 114, 41, 51, 35, 217, 248, 165, 245, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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