Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12fb163ebfefdeb4117019647a92e8c8d0f14755a20b8fcfac5ec57beeb9663c

Tx prefix hash: 536327d59be6c8d5a1d66d44c45fb79f6a81fc7e112cabba25e524d30980a479
Tx public key: f5bda9daf1cc70d7387a3b5ba112faed8fd46d493efbc20f3356c7f577e53137
Timestamp: 1704564984 Timestamp [UCT]: 2024-01-06 18:16:24 Age [y:d:h:m:s]: 00:360:16:39:49
Block: 929578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258239 RingCT/type: yes/0
Extra: 01f5bda9daf1cc70d7387a3b5ba112faed8fd46d493efbc20f3356c7f577e5313702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e8f208867e1dcff3c47e477b8975c57935a4da872ae8d971d0862da6e3fe1fc 0.600000000000 1387454 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": 929588, "vin": [ { "gen": { "height": 929578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e8f208867e1dcff3c47e477b8975c57935a4da872ae8d971d0862da6e3fe1fc" } } ], "extra": [ 1, 245, 189, 169, 218, 241, 204, 112, 215, 56, 122, 59, 91, 161, 18, 250, 237, 143, 212, 109, 73, 62, 251, 194, 15, 51, 86, 199, 245, 119, 229, 49, 55, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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