Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcce0897ba10007c4e40e7e8f265c6825c1eb5a326d69d5c2fe58fce096e9e6c

Tx prefix hash: 4e0e85abf2f8f8328644ac0271abd2e4d1949149d8e63820940c104d22c1ad98
Tx public key: b4d4cfcba98f3dd0e8a9b54d696fd83494e6611140cb54f7d4304411c0a2b07b
Timestamp: 1694872254 Timestamp [UCT]: 2023-09-16 13:50:54 Age [y:d:h:m:s]: 02:023:22:33:34
Block: 849420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536738 RingCT/type: yes/0
Extra: 01b4d4cfcba98f3dd0e8a9b54d696fd83494e6611140cb54f7d4304411c0a2b07b02110000000c4b8f5122000000000000000000

1 output(s) for total of 0.940846961000 dcy

stealth address amount amount idx
00: 189e47b7d337e520d39788262e8afbdcf0e5e1873fbbb8b673f91f02fb520250 0.940846961000 1303084 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": 849430, "vin": [ { "gen": { "height": 849420 } } ], "vout": [ { "amount": 940846961, "target": { "key": "189e47b7d337e520d39788262e8afbdcf0e5e1873fbbb8b673f91f02fb520250" } } ], "extra": [ 1, 180, 212, 207, 203, 169, 143, 61, 208, 232, 169, 181, 77, 105, 111, 216, 52, 148, 230, 97, 17, 64, 203, 84, 247, 212, 48, 68, 17, 192, 162, 176, 123, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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