Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd49168840e074e9e192bb126e11693975884af3b05530b0ac64c2eb53a3532c

Tx prefix hash: c478cf6ac0028fec94d1b1b791428b86c938d3b6d1de91a932d23f8d9f50fb13
Tx public key: c7fc2146b18ab9d635b834e9af46641a3bc1683ddfe2cca1c1abfbdbfe75f525
Timestamp: 1634049595 Timestamp [UCT]: 2021-10-12 14:39:55 Age [y:d:h:m:s]: 03:197:01:49:22
Block: 351707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918280 RingCT/type: yes/0
Extra: 01c7fc2146b18ab9d635b834e9af46641a3bc1683ddfe2cca1c1abfbdbfe75f5250211000000103fc41461000000000000000000

1 output(s) for total of 41.942729324000 dcy

stealth address amount amount idx
00: 60f80a6b08b1e1b63619d0572ea7665d9138ec71f83be4540ad36bc886eee5fd 41.942729324000 719135 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": 351717, "vin": [ { "gen": { "height": 351707 } } ], "vout": [ { "amount": 41942729324, "target": { "key": "60f80a6b08b1e1b63619d0572ea7665d9138ec71f83be4540ad36bc886eee5fd" } } ], "extra": [ 1, 199, 252, 33, 70, 177, 138, 185, 214, 53, 184, 52, 233, 175, 70, 100, 26, 59, 193, 104, 61, 223, 226, 204, 161, 193, 171, 251, 219, 254, 117, 245, 37, 2, 17, 0, 0, 0, 16, 63, 196, 20, 97, 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