Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f9114aa78e22a64adbd28fd9479fe8607b32f310bb72327ac9084122a78636

Tx prefix hash: 6ca3ac17fc8ed1fbe6fba71710a417fe8e768efee485abc02b2aaf5cb08d279d
Tx public key: f8a5c54589cc2421060c690d9d8df61e6104960ef7729af66f8c336f8c7a0f13
Timestamp: 1703916471 Timestamp [UCT]: 2023-12-30 06:07:51 Age [y:d:h:m:s]: 01:033:04:34:10
Block: 924207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284813 RingCT/type: yes/0
Extra: 01f8a5c54589cc2421060c690d9d8df61e6104960ef7729af66f8c336f8c7a0f130211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09cec175d4b19a06b509eefc2eabccf1683fdef1c9db431f414b310200d5b766 0.600000000000 1381951 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": 924217, "vin": [ { "gen": { "height": 924207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09cec175d4b19a06b509eefc2eabccf1683fdef1c9db431f414b310200d5b766" } } ], "extra": [ 1, 248, 165, 197, 69, 137, 204, 36, 33, 6, 12, 105, 13, 157, 141, 246, 30, 97, 4, 150, 14, 247, 114, 154, 246, 111, 140, 51, 111, 140, 122, 15, 19, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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