Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aefc5b08a8ff24c1a3ab14d7a7bb2d902f499ea362a616e1df055f32e9efee6d

Tx prefix hash: eff8948c74a536d07f03af041f02ae765acda370a2e8b2b67df6f422a4854b73
Tx public key: b8a5322ea4d5e12b72cf4aace9652190a4133607416c2a077b1223b649b75028
Timestamp: 1706455626 Timestamp [UCT]: 2024-01-28 15:27:06 Age [y:d:h:m:s]: 01:028:14:49:49
Block: 945238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281502 RingCT/type: yes/0
Extra: 01b8a5322ea4d5e12b72cf4aace9652190a4133607416c2a077b1223b649b7502802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23fa43ea52187c668e1d0c2e025a903c17fd513519cd25b5bc28b60dfa6855e 0.600000000000 1403548 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": 945248, "vin": [ { "gen": { "height": 945238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23fa43ea52187c668e1d0c2e025a903c17fd513519cd25b5bc28b60dfa6855e" } } ], "extra": [ 1, 184, 165, 50, 46, 164, 213, 225, 43, 114, 207, 74, 172, 233, 101, 33, 144, 164, 19, 54, 7, 65, 108, 42, 7, 123, 18, 35, 182, 73, 183, 80, 40, 2, 17, 0, 0, 0, 6, 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