Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0aedc5e230d1082ae76ebe23d9727e4ca4ee341ae77d6956d4cb4684377eac9

Tx prefix hash: 858bc524fe9791b7fa01a2ec1b57323b60880a7e5b6ceb798385cafaf0f7bc82
Tx public key: 798b7f37264991e2e4e5246c7bae6868b47894d228d3dda63df716bbeb6f8356
Timestamp: 1705240116 Timestamp [UCT]: 2024-01-14 13:48:36 Age [y:d:h:m:s]: 01:309:19:49:41
Block: 935184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480248 RingCT/type: yes/0
Extra: 01798b7f37264991e2e4e5246c7bae6868b47894d228d3dda63df716bbeb6f835602110000000541ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee60647548f9fe16fe3eada55e77c94dbf2c0691d909075100e4c01e4802a5e9 0.600000000000 1393200 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": 935194, "vin": [ { "gen": { "height": 935184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee60647548f9fe16fe3eada55e77c94dbf2c0691d909075100e4c01e4802a5e9" } } ], "extra": [ 1, 121, 139, 127, 55, 38, 73, 145, 226, 228, 229, 36, 108, 123, 174, 104, 104, 180, 120, 148, 210, 40, 211, 221, 166, 61, 247, 22, 187, 235, 111, 131, 86, 2, 17, 0, 0, 0, 5, 65, 238, 28, 155, 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