Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e18c41a47da9abb23173607c4ee5c229022a2059fb23ec33bfeb9170346f5f

Tx prefix hash: 93b0be3c0b97133973ef2a092e4922e2c311f04da911848ddc737a2cb48192cc
Tx public key: 0d2b48a0d93aa7873fce754a094fef67ed4830fc40e0dc6dacb250ef3d0f5335
Timestamp: 1669098804 Timestamp [UCT]: 2022-11-22 06:33:24 Age [y:d:h:m:s]: 01:364:07:01:51
Block: 636474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521371 RingCT/type: yes/0
Extra: 010d2b48a0d93aa7873fce754a094fef67ed4830fc40e0dc6dacb250ef3d0f533502110000000852542ceb000000000000000000

1 output(s) for total of 4.776364166000 dcy

stealth address amount amount idx
00: d48fafd7c630e681c7d1625b092dc38aebf968f0522cb871d292d52b7c3abc0b 4.776364166000 1075914 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": 636484, "vin": [ { "gen": { "height": 636474 } } ], "vout": [ { "amount": 4776364166, "target": { "key": "d48fafd7c630e681c7d1625b092dc38aebf968f0522cb871d292d52b7c3abc0b" } } ], "extra": [ 1, 13, 43, 72, 160, 217, 58, 167, 135, 63, 206, 117, 74, 9, 79, 239, 103, 237, 72, 48, 252, 64, 224, 220, 109, 172, 178, 80, 239, 61, 15, 83, 53, 2, 17, 0, 0, 0, 8, 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