Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97e24e55665e4baa3467c9f6dca72d7a0408062754b7e6a5151ac734787f48e

Tx prefix hash: cc05e62a5f484292281ed9655eb3472bd4ed9b2c0d10e7453b6a844ca45928b4
Tx public key: b60ba51d65e3cc04f66d734035e5edbd3c34724e8c30075c223e03611d829fe2
Timestamp: 1712582784 Timestamp [UCT]: 2024-04-08 13:26:24 Age [y:d:h:m:s]: 01:037:21:53:42
Block: 996036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288089 RingCT/type: yes/0
Extra: 01b60ba51d65e3cc04f66d734035e5edbd3c34724e8c30075c223e03611d829fe202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd278716e12a5aa9d7e7475e555801b066450a6c78a420a658478d6698ba78c8 0.600000000000 1456452 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": 996046, "vin": [ { "gen": { "height": 996036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd278716e12a5aa9d7e7475e555801b066450a6c78a420a658478d6698ba78c8" } } ], "extra": [ 1, 182, 11, 165, 29, 101, 227, 204, 4, 246, 109, 115, 64, 53, 229, 237, 189, 60, 52, 114, 78, 140, 48, 7, 92, 34, 62, 3, 97, 29, 130, 159, 226, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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