Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c4627b1ce1e9a3aec5424073944539aa3d575334c9d92a68aa80d98964bea4c

Tx prefix hash: c00f329e0969075737dea2b1d19ea6be3e1061c85c4e5033d290ce76089d08fd
Tx public key: 47bfc1ab769ccc32b0a63800903712092e0bc2e6e1eba3a3f64545074e56bc54
Timestamp: 1672583683 Timestamp [UCT]: 2023-01-01 14:34:43 Age [y:d:h:m:s]: 02:059:03:37:50
Block: 665310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563941 RingCT/type: yes/0
Extra: 0147bfc1ab769ccc32b0a63800903712092e0bc2e6e1eba3a3f64545074e56bc5402110000000752542ceb000000000000000000

1 output(s) for total of 3.833114133000 dcy

stealth address amount amount idx
00: 80f12cd34f056a00d7dc3001685c64f45210402b849185499805cb251ad6813b 3.833114133000 1106341 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": 665320, "vin": [ { "gen": { "height": 665310 } } ], "vout": [ { "amount": 3833114133, "target": { "key": "80f12cd34f056a00d7dc3001685c64f45210402b849185499805cb251ad6813b" } } ], "extra": [ 1, 71, 191, 193, 171, 118, 156, 204, 50, 176, 166, 56, 0, 144, 55, 18, 9, 46, 11, 194, 230, 225, 235, 163, 163, 246, 69, 69, 7, 78, 86, 188, 84, 2, 17, 0, 0, 0, 7, 82, 84, 44, 235, 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