Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04645e9eb81f3b7a08e1e0845c3f0c7764f9a41535757e90c791f250a786f29c

Tx prefix hash: cce7f4c13d2d0f83805f9466204441b90022f125e4818943e482aa80f4e7af40
Tx public key: dcd8ebea151bf73f18bff6492917b6eda31fee84d0def979f1c742a1517ed55d
Timestamp: 1580811903 Timestamp [UCT]: 2020-02-04 10:25:03 Age [y:d:h:m:s]: 05:038:23:27:57
Block: 58604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179725 RingCT/type: yes/0
Extra: 01dcd8ebea151bf73f18bff6492917b6eda31fee84d0def979f1c742a1517ed55d0211000000064ac5aa02000000000000000000

1 output(s) for total of 392.483533408000 dcy

stealth address amount amount idx
00: 990f319eea8542d53648eb5b029cb3b97a022472c6ac63135dd3d97e65b8e80a 392.483533408000 108254 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": 58614, "vin": [ { "gen": { "height": 58604 } } ], "vout": [ { "amount": 392483533408, "target": { "key": "990f319eea8542d53648eb5b029cb3b97a022472c6ac63135dd3d97e65b8e80a" } } ], "extra": [ 1, 220, 216, 235, 234, 21, 27, 247, 63, 24, 191, 246, 73, 41, 23, 182, 237, 163, 31, 238, 132, 208, 222, 249, 121, 241, 199, 66, 161, 81, 126, 213, 93, 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