Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dd392681561e53aa607b790687ac49326d6e3e9fc5fe505ddbf3d9a442d9b6c

Tx prefix hash: 392ebea5d2d396e6d3c06952a379f8edc91ef5a73dc0e89707cbf286214ef2c8
Tx public key: d6b90907be5ec3ac477164c3a88737142bd1b9ebf021f83fc5373bcbaee1fe3b
Timestamp: 1730035930 Timestamp [UCT]: 2024-10-27 13:32:10 Age [y:d:h:m:s]: 00:028:01:58:31
Block: 1140717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20070 RingCT/type: yes/0
Extra: 01d6b90907be5ec3ac477164c3a88737142bd1b9ebf021f83fc5373bcbaee1fe3b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87172645ecc8f55e4bf1187d59406a56be4f289e309cb5d04fbc7574df50aad7 0.600000000000 1624520 of 15

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": 1140727, "vin": [ { "gen": { "height": 1140717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87172645ecc8f55e4bf1187d59406a56be4f289e309cb5d04fbc7574df50aad7" } } ], "extra": [ 1, 214, 185, 9, 7, 190, 94, 195, 172, 71, 113, 100, 195, 168, 135, 55, 20, 43, 209, 185, 235, 240, 33, 248, 63, 197, 55, 59, 203, 174, 225, 254, 59, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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