Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1792f53e2e28bde5edcac5913a35b38c36da9feaba06f8a91c221fb47903f54c

Tx prefix hash: 5b8f250a5ae3173fcd0dd28f7b88a87ecd0f67e232ba87fb47ef967ed1e2fcd1
Tx public key: 90cd264f9e31f340383211d1b8faa0794e49f90ae3962985e74b2d21c5332985
Timestamp: 1682280396 Timestamp [UCT]: 2023-04-23 20:06:36 Age [y:d:h:m:s]: 01:307:20:48:25
Block: 745090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481260 RingCT/type: yes/0
Extra: 0190cd264f9e31f340383211d1b8faa0794e49f90ae3962985e74b2d21c533298502110000000275e3f0e9000000000000000000

1 output(s) for total of 2.085488209000 dcy

stealth address amount amount idx
00: d1318ea8fedb1759f4cca058242054103060dc70dfb673d77d5348e92e8edd8a 2.085488209000 1192507 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": 745100, "vin": [ { "gen": { "height": 745090 } } ], "vout": [ { "amount": 2085488209, "target": { "key": "d1318ea8fedb1759f4cca058242054103060dc70dfb673d77d5348e92e8edd8a" } } ], "extra": [ 1, 144, 205, 38, 79, 158, 49, 243, 64, 56, 50, 17, 209, 184, 250, 160, 121, 78, 73, 249, 10, 227, 150, 41, 133, 231, 75, 45, 33, 197, 51, 41, 133, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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