Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e972b78e0cee1957ee43b9cf3a543b800e7b7f0a3619ac42b9e00c41b1bf77b1

Tx prefix hash: 05297f642fac0b9e04b9f24913af3aebc64d594f7dadd15f7795b14ddb8fe92b
Tx public key: 74291aa5f13b37437d1cd0bbe584f9948fc74cf7410ea7d12759c685de9fa5e7
Timestamp: 1582803725 Timestamp [UCT]: 2020-02-27 11:42:05 Age [y:d:h:m:s]: 04:304:21:07:18
Block: 73007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111176 RingCT/type: yes/0
Extra: 0174291aa5f13b37437d1cd0bbe584f9948fc74cf7410ea7d12759c685de9fa5e70211000000074943cd9f000000000000000000

1 output(s) for total of 351.640024488000 dcy

stealth address amount amount idx
00: 5e36b320313cabfa5340a269e85dcc910e428d021a70c5d9099a91420c56e51c 351.640024488000 134654 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": 73017, "vin": [ { "gen": { "height": 73007 } } ], "vout": [ { "amount": 351640024488, "target": { "key": "5e36b320313cabfa5340a269e85dcc910e428d021a70c5d9099a91420c56e51c" } } ], "extra": [ 1, 116, 41, 26, 165, 241, 59, 55, 67, 125, 28, 208, 187, 229, 132, 249, 148, 143, 199, 76, 247, 65, 14, 167, 209, 39, 89, 198, 133, 222, 159, 165, 231, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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