Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95fea75dc2cc2ca17e6141fb75f06f9e41510f45a7728d1e37a6f2a0f132b50

Tx prefix hash: d198e9f3f56824d23a3a4fff88c37260650fb1f85633f652266837a8c562839d
Tx public key: f4b960d1a78677e059de65cdb9ddc1049d10b734e8678883351422429d282fe0
Timestamp: 1710721214 Timestamp [UCT]: 2024-03-18 00:20:14 Age [y:d:h:m:s]: 00:344:11:57:43
Block: 980651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246273 RingCT/type: yes/0
Extra: 01f4b960d1a78677e059de65cdb9ddc1049d10b734e8678883351422429d282fe0021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a9e2d1e1d869356c66be85451c3823a09ed054c979a9e6b36a01be555d10b5 0.600000000000 1440732 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": 980661, "vin": [ { "gen": { "height": 980651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a9e2d1e1d869356c66be85451c3823a09ed054c979a9e6b36a01be555d10b5" } } ], "extra": [ 1, 244, 185, 96, 209, 167, 134, 119, 224, 89, 222, 101, 205, 185, 221, 193, 4, 157, 16, 183, 52, 232, 103, 136, 131, 53, 20, 34, 66, 157, 40, 47, 224, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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