Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72aedf389c9e28bab5e80b14adfb83b399e93f18f225228dcc448d5ccdb9f108

Tx prefix hash: c5cb40a7335422405c7c1e73deb252349c5aa212e642bbfc4ab3490774994b5e
Tx public key: aad36dd83e570b3e9ca56ee41b4d3e74de23187875a98b897e919fd01dba8f2c
Timestamp: 1577530655 Timestamp [UCT]: 2019-12-28 10:57:35 Age [y:d:h:m:s]: 05:010:21:27:30
Block: 33414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157924 RingCT/type: yes/0
Extra: 01aad36dd83e570b3e9ca56ee41b4d3e74de23187875a98b897e919fd01dba8f2c0211000000034ac5aa02000000000000000000

1 output(s) for total of 475.648798966000 dcy

stealth address amount amount idx
00: 2aecf9c318cf2741972a1c713e6af74e8e7f832d153a4e8e7d2e82ac2461fba7 475.648798966000 55939 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": 33424, "vin": [ { "gen": { "height": 33414 } } ], "vout": [ { "amount": 475648798966, "target": { "key": "2aecf9c318cf2741972a1c713e6af74e8e7f832d153a4e8e7d2e82ac2461fba7" } } ], "extra": [ 1, 170, 211, 109, 216, 62, 87, 11, 62, 156, 165, 110, 228, 27, 77, 62, 116, 222, 35, 24, 120, 117, 169, 139, 137, 126, 145, 159, 208, 29, 186, 143, 44, 2, 17, 0, 0, 0, 3, 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