Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7669430cfd3cbbc2d2ae4cf657e255bd4f8e36ddd66451a47014e8bdf386358

Tx prefix hash: 768448e16e42eb5bd3067e924c8d48c5e91fdea53fe29fdbf85711a400d32e33
Tx public key: 90ae705d31e5ba3893cbce89dea6f4ecbf91a8c3616f3a9ed2cf2b1b748ab41d
Timestamp: 1710387067 Timestamp [UCT]: 2024-03-14 03:31:07 Age [y:d:h:m:s]: 00:346:13:32:48
Block: 977874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247760 RingCT/type: yes/0
Extra: 0190ae705d31e5ba3893cbce89dea6f4ecbf91a8c3616f3a9ed2cf2b1b748ab41d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 930da72f8e4a87a690c2ca3ec313a71cd5544aaf014b6d5b80b6fd8e6d4964a8 0.600000000000 1437881 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": 977884, "vin": [ { "gen": { "height": 977874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "930da72f8e4a87a690c2ca3ec313a71cd5544aaf014b6d5b80b6fd8e6d4964a8" } } ], "extra": [ 1, 144, 174, 112, 93, 49, 229, 186, 56, 147, 203, 206, 137, 222, 166, 244, 236, 191, 145, 168, 195, 97, 111, 58, 158, 210, 207, 43, 27, 116, 138, 180, 29, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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