Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef74c7fdf33180dcea3e36ec3f706ddd11b2ead637ef4ed09691004cc051b4f2

Tx prefix hash: 7462ac7785f741e4b4189fc486166059860963f64be52119aa09644c1a60107a
Tx public key: 94ae4de8ac305ac04c378d5f39e0916c3f22daec6c6724ea6c381643363c364b
Timestamp: 1674074720 Timestamp [UCT]: 2023-01-18 20:45:20 Age [y:d:h:m:s]: 02:041:00:06:58
Block: 677672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550936 RingCT/type: yes/0
Extra: 0194ae4de8ac305ac04c378d5f39e0916c3f22daec6c6724ea6c381643363c364b02110000000352542ceb000000000000000000

1 output(s) for total of 3.488119017000 dcy

stealth address amount amount idx
00: b2eb032e9787cb5ce085717b26a58985a5e1d59dccc8ec7a777b97851df6ebc4 3.488119017000 1119461 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": 677682, "vin": [ { "gen": { "height": 677672 } } ], "vout": [ { "amount": 3488119017, "target": { "key": "b2eb032e9787cb5ce085717b26a58985a5e1d59dccc8ec7a777b97851df6ebc4" } } ], "extra": [ 1, 148, 174, 77, 232, 172, 48, 90, 192, 76, 55, 141, 95, 57, 224, 145, 108, 63, 34, 218, 236, 108, 103, 36, 234, 108, 56, 22, 67, 54, 60, 54, 75, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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