Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d8f486940b9136d5c1ca834f38d38f9bc4ca62352e676891c180dd1854f126f

Tx prefix hash: 9500aecca0643e470fbbdc4847bd6430a2f7adbed3d0e97a3c828f740264c3c3
Tx public key: bf40bb4e24817d9bf7cb1214f4e2b8d083923d4d0a0c5176e882a35f9ad719ec
Timestamp: 1723392377 Timestamp [UCT]: 2024-08-11 16:06:17 Age [y:d:h:m:s]: 00:310:23:21:18
Block: 1085681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222055 RingCT/type: yes/0
Extra: 01bf40bb4e24817d9bf7cb1214f4e2b8d083923d4d0a0c5176e882a35f9ad719ec021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5efe550bf6458f2a6fd8dd702df990fd7828b743a1c14052fd3b3d1f78d6e048 0.600000000000 1560270 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": 1085691, "vin": [ { "gen": { "height": 1085681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5efe550bf6458f2a6fd8dd702df990fd7828b743a1c14052fd3b3d1f78d6e048" } } ], "extra": [ 1, 191, 64, 187, 78, 36, 129, 125, 155, 247, 203, 18, 20, 244, 226, 184, 208, 131, 146, 61, 77, 10, 12, 81, 118, 232, 130, 163, 95, 154, 215, 25, 236, 2, 17, 0, 0, 0, 1, 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