Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9523d1776de3eb4344eb187feb5ff96a4f3d17d28d22f549e8531d1ca9ff9bce

Tx prefix hash: 2544bc738f34efd5abf15fa7f8180ce20cf9778e26d1ca5e5955e320f4745b44
Tx public key: 40865c43d717a6b0f997f8f1695b92c9b8586c8befd2a327c59091ae2650c1d6
Timestamp: 1721442915 Timestamp [UCT]: 2024-07-20 02:35:15 Age [y:d:h:m:s]: 00:247:20:19:33
Block: 1069559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177001 RingCT/type: yes/0
Extra: 0140865c43d717a6b0f997f8f1695b92c9b8586c8befd2a327c59091ae2650c1d6021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a962c216fbf86726714930ee0f3343ca84a820805412001aaa9b37d1e5abbeb 0.600000000000 1541020 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": 1069569, "vin": [ { "gen": { "height": 1069559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a962c216fbf86726714930ee0f3343ca84a820805412001aaa9b37d1e5abbeb" } } ], "extra": [ 1, 64, 134, 92, 67, 215, 23, 166, 176, 249, 151, 248, 241, 105, 91, 146, 201, 184, 88, 108, 139, 239, 210, 163, 39, 197, 144, 145, 174, 38, 80, 193, 214, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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