Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06ec8d538b52fcd5f5b6828523d2f6ef9f58a4bc7965783e3c375f0e39cfce5f

Tx prefix hash: a3b303a93ca340616626eaf4dd29994248142d9db173fa5f9c389a679ca95a4c
Tx public key: 797e23da0036e099ab43048af9fda35daeed3442fc7d875aa982dbd3e210b806
Timestamp: 1590431519 Timestamp [UCT]: 2020-05-25 18:31:59 Age [y:d:h:m:s]: 05:160:00:07:34
Block: 103156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1298957 RingCT/type: yes/0
Extra: 01797e23da0036e099ab43048af9fda35daeed3442fc7d875aa982dbd3e210b8060211000002bc25a1e897000000000000000000

1 output(s) for total of 279.384371207000 dcy

stealth address amount amount idx
00: 15e298c9d7682c9adde2ea27876e4370a90cf752006bd998d857a78c26c28a46 279.384371207000 181033 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": 103166, "vin": [ { "gen": { "height": 103156 } } ], "vout": [ { "amount": 279384371207, "target": { "key": "15e298c9d7682c9adde2ea27876e4370a90cf752006bd998d857a78c26c28a46" } } ], "extra": [ 1, 121, 126, 35, 218, 0, 54, 224, 153, 171, 67, 4, 138, 249, 253, 163, 93, 174, 237, 52, 66, 252, 125, 135, 90, 169, 130, 219, 211, 226, 16, 184, 6, 2, 17, 0, 0, 2, 188, 37, 161, 232, 151, 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