Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9fd3f2b9778a6c10d389fcf726955c987e8caa4805288c76b1e5a54384709f2

Tx prefix hash: 2be78725c35892c6d0e5fd0dc1ffe9b3d1e236dce3dae775b7279e36723bb4f1
Tx public key: fe83115a698d67a9ebf4c923b099a967fce3136d032acd65b38949dbf15335c3
Timestamp: 1725942305 Timestamp [UCT]: 2024-09-10 04:25:05 Age [y:d:h:m:s]: 01:057:20:59:55
Block: 1106821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299772 RingCT/type: yes/0
Extra: 01fe83115a698d67a9ebf4c923b099a967fce3136d032acd65b38949dbf15335c302110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96283dbd658fda86228c3d1ec7f8c26ad251e01646ca1772ae6cf94e1411e0fe 0.600000000000 1584422 of 15

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": 1106831, "vin": [ { "gen": { "height": 1106821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96283dbd658fda86228c3d1ec7f8c26ad251e01646ca1772ae6cf94e1411e0fe" } } ], "extra": [ 1, 254, 131, 17, 90, 105, 141, 103, 169, 235, 244, 201, 35, 176, 153, 169, 103, 252, 227, 19, 109, 3, 42, 205, 101, 179, 137, 73, 219, 241, 83, 53, 195, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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