Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db587c08b73da42110dac8a09aa7f1219cf0f80dd4e175f79c30d1d7aa1de2b5

Tx prefix hash: e045ba4ae264900ad7f3a8b22405d5dec2b378b5e938c16137c53cb629e86c48
Tx public key: 9f401381b0f1b625d2892c55f23ec15a2455e99f4267dd325fe81430aaf7b79e
Timestamp: 1583449474 Timestamp [UCT]: 2020-03-05 23:04:34 Age [y:d:h:m:s]: 04:298:07:25:22
Block: 77015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107816 RingCT/type: yes/0
Extra: 019f401381b0f1b625d2892c55f23ec15a2455e99f4267dd325fe81430aaf7b79e0211000000064ac5aa02000000000000000000

1 output(s) for total of 341.050058902000 dcy

stealth address amount amount idx
00: ce9fa59ebbc25788db97cc30925f93d6e60a60a4e583ea45f41a729ef677d3dc 341.050058902000 141797 of 0

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": 77025, "vin": [ { "gen": { "height": 77015 } } ], "vout": [ { "amount": 341050058902, "target": { "key": "ce9fa59ebbc25788db97cc30925f93d6e60a60a4e583ea45f41a729ef677d3dc" } } ], "extra": [ 1, 159, 64, 19, 129, 176, 241, 182, 37, 210, 137, 44, 85, 242, 62, 193, 90, 36, 85, 233, 159, 66, 103, 221, 50, 95, 232, 20, 48, 170, 247, 183, 158, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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