Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4b5333a28c1be8690bde8b7dbfb85b3deef47173c15e329f15b53d6bb2f9f5

Tx prefix hash: 684fd299409ef6d0c75214de6d389a7afc4a29ad90f77a2bd1d0599ec2f6dfba
Tx public key: 34c8c2fae3f1a7e9900689c50fc4e40355519968928793a3e5d4386421d00b2b
Timestamp: 1611800727 Timestamp [UCT]: 2021-01-28 02:25:27 Age [y:d:h:m:s]: 04:277:21:15:12
Block: 186610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215653 RingCT/type: yes/0
Extra: 0134c8c2fae3f1a7e9900689c50fc4e40355519968928793a3e5d4386421d00b2b0211000000cd4ea414e5000000000000000000

1 output(s) for total of 147.811009243000 dcy

stealth address amount amount idx
00: ef35d058f8fc0c6d0952832182a81266795ff099e0d671698ee455fcf455b12e 147.811009243000 367849 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": 186620, "vin": [ { "gen": { "height": 186610 } } ], "vout": [ { "amount": 147811009243, "target": { "key": "ef35d058f8fc0c6d0952832182a81266795ff099e0d671698ee455fcf455b12e" } } ], "extra": [ 1, 52, 200, 194, 250, 227, 241, 167, 233, 144, 6, 137, 197, 15, 196, 228, 3, 85, 81, 153, 104, 146, 135, 147, 163, 229, 212, 56, 100, 33, 208, 11, 43, 2, 17, 0, 0, 0, 205, 78, 164, 20, 229, 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