Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec18473f864c9a1e8b55f3ed8500fe78fe3e21ff2d02ca03f3dead02f8246d6e

Tx prefix hash: 940af4475fc24bfe63d8c95da7ad5804aca4c0f834b1b09a43048236d2b871a6
Tx public key: 33e5babfeeb574aaf4bcf88d12aaa558f7f837829b18a17bee8430678f5ccc25
Timestamp: 1577447927 Timestamp [UCT]: 2019-12-27 11:58:47 Age [y:d:h:m:s]: 05:078:00:57:09
Block: 32851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205569 RingCT/type: yes/0
Extra: 0133e5babfeeb574aaf4bcf88d12aaa558f7f837829b18a17bee8430678f5ccc25021100000002d81c26c0000000000000000000

1 output(s) for total of 477.696278599000 dcy

stealth address amount amount idx
00: 12545ae7b7114e562ff233f70668df257a8efa9ba74c3cdc54f4ebb2867a80b0 477.696278599000 54732 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": 32861, "vin": [ { "gen": { "height": 32851 } } ], "vout": [ { "amount": 477696278599, "target": { "key": "12545ae7b7114e562ff233f70668df257a8efa9ba74c3cdc54f4ebb2867a80b0" } } ], "extra": [ 1, 51, 229, 186, 191, 238, 181, 116, 170, 244, 188, 248, 141, 18, 170, 165, 88, 247, 248, 55, 130, 155, 24, 161, 123, 238, 132, 48, 103, 143, 92, 204, 37, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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