Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b7955bd0ff50b7ea3b6e17335d635775a2200fcd31bd2bfd5b0020111914c63

Tx prefix hash: 4e43fb20d9410431bdedbe9625e3e2146c562bab1bd29c32c851327c63008c5d
Tx public key: c3dfcd29882ca68055bcfae3cc73c50eb35a83cfdc5917a9d4f9fa3a4cec564c
Timestamp: 1695963301 Timestamp [UCT]: 2023-09-29 04:55:01 Age [y:d:h:m:s]: 01:188:16:48:28
Block: 858488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395904 RingCT/type: yes/0
Extra: 01c3dfcd29882ca68055bcfae3cc73c50eb35a83cfdc5917a9d4f9fa3a4cec564c021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.877956351000 dcy

stealth address amount amount idx
00: 6aee6d0ffbefb9185e27ad93b8266784f4ae8bb0e147d63cf84135a344be7a9a 0.877956351000 1312664 of 0

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": 858498, "vin": [ { "gen": { "height": 858488 } } ], "vout": [ { "amount": 877956351, "target": { "key": "6aee6d0ffbefb9185e27ad93b8266784f4ae8bb0e147d63cf84135a344be7a9a" } } ], "extra": [ 1, 195, 223, 205, 41, 136, 44, 166, 128, 85, 188, 250, 227, 204, 115, 197, 14, 179, 90, 131, 207, 220, 89, 23, 169, 212, 249, 250, 58, 76, 236, 86, 76, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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