Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82366ab31f03e115a4a84c7ca81ecb065bef09907712d0815f647e1e1eab8d86

Tx prefix hash: 743e8c967ca91f7a37340fb94fd61fd245e05de87790b365cb303e6dea9d6d18
Tx public key: 75018bae1878487a573dbd0f0a9ca0dd0141055ecec26de97931d067c8e894a7
Timestamp: 1580666968 Timestamp [UCT]: 2020-02-02 18:09:28 Age [y:d:h:m:s]: 05:133:16:17:27
Block: 57182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247598 RingCT/type: yes/0
Extra: 0175018bae1878487a573dbd0f0a9ca0dd0141055ecec26de97931d067c8e894a702110000000149b77a3d000000000000000000

1 output(s) for total of 396.771634864000 dcy

stealth address amount amount idx
00: a8bdf672c8776a2b76b4b0d5b05ecefe99f352cdaee1ab2a49ee2f19678c0a18 396.771634864000 105524 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": 57192, "vin": [ { "gen": { "height": 57182 } } ], "vout": [ { "amount": 396771634864, "target": { "key": "a8bdf672c8776a2b76b4b0d5b05ecefe99f352cdaee1ab2a49ee2f19678c0a18" } } ], "extra": [ 1, 117, 1, 139, 174, 24, 120, 72, 122, 87, 61, 189, 15, 10, 156, 160, 221, 1, 65, 5, 94, 206, 194, 109, 233, 121, 49, 208, 103, 200, 232, 148, 167, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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