Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6e86106a903d643677a0b5595c0e7822efa41d1dddc68432b8b63bedab0eb5d

Tx prefix hash: d381c754fdd090e397636adb9e5da2f9c6e24a5a2b3ec7901bac73225416e819
Tx public key: fa9d17d249fcb1e3fac5850699224a4fbe62c3d968e7c7d707d3cb12309f2621
Timestamp: 1724076726 Timestamp [UCT]: 2024-08-19 14:12:06 Age [y:d:h:m:s]: 00:268:03:18:08
Block: 1091359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191536 RingCT/type: yes/0
Extra: 01fa9d17d249fcb1e3fac5850699224a4fbe62c3d968e7c7d707d3cb12309f262102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10b25ccdf31bebe85bac4c22591292c14745dbbb5471bf79dc5ddc5ff135a29 0.600000000000 1565990 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": 1091369, "vin": [ { "gen": { "height": 1091359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10b25ccdf31bebe85bac4c22591292c14745dbbb5471bf79dc5ddc5ff135a29" } } ], "extra": [ 1, 250, 157, 23, 210, 73, 252, 177, 227, 250, 197, 133, 6, 153, 34, 74, 79, 190, 98, 195, 217, 104, 231, 199, 215, 7, 211, 203, 18, 48, 159, 38, 33, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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