Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d95e8e23c5cb60a2c6a37f665622e0be543658152f306ec109d42ed5b0d435

Tx prefix hash: 51a8697119e4d5e560bd8281933ca87cb7176e875530a1cc82bd1aac6170109e
Tx public key: 3154b493f66ca35742b45d5acd5a9447f4b9f35c1903104ec7c8e5a26fbf27da
Timestamp: 1574110092 Timestamp [UCT]: 2019-11-18 20:48:12 Age [y:d:h:m:s]: 05:058:09:58:22
Block: 12152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1184845 RingCT/type: yes/0
Extra: 013154b493f66ca35742b45d5acd5a9447f4b9f35c1903104ec7c8e5a26fbf27da021100000001ccefb800000000000000000000

1 output(s) for total of 559.437073011000 dcy

stealth address amount amount idx
00: 476b946c45161383384cb42d905156fbe5e4c0f6bb12b6f419756a3c24097ffd 559.437073011000 13241 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": 12162, "vin": [ { "gen": { "height": 12152 } } ], "vout": [ { "amount": 559437073011, "target": { "key": "476b946c45161383384cb42d905156fbe5e4c0f6bb12b6f419756a3c24097ffd" } } ], "extra": [ 1, 49, 84, 180, 147, 246, 108, 163, 87, 66, 180, 93, 90, 205, 90, 148, 71, 244, 185, 243, 92, 25, 3, 16, 78, 199, 200, 229, 162, 111, 191, 39, 218, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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