Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a5e742a2bf2c0aae32535a669d2a41b4d403b824f4ebb7023b2a0a4bdd26b8

Tx prefix hash: 4843505401cf7fe14322f182606216ddac4da7b5e34738be5b43f9ce4da1b5f2
Tx public key: 0f81f206428cd427826a8bfb8b64709ceba5f8653c8c8ffaca6027340119f377
Timestamp: 1724518914 Timestamp [UCT]: 2024-08-24 17:01:54 Age [y:d:h:m:s]: 00:225:14:42:33
Block: 1095041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161082 RingCT/type: yes/0
Extra: 010f81f206428cd427826a8bfb8b64709ceba5f8653c8c8ffaca6027340119f377021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a8174483daeac2ad62d6d5b14e6e9b2fa6bce1dd912cf70eb655f37aa1c3ac3 0.600000000000 1570172 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": 1095051, "vin": [ { "gen": { "height": 1095041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a8174483daeac2ad62d6d5b14e6e9b2fa6bce1dd912cf70eb655f37aa1c3ac3" } } ], "extra": [ 1, 15, 129, 242, 6, 66, 140, 212, 39, 130, 106, 139, 251, 139, 100, 112, 156, 235, 165, 248, 101, 60, 140, 143, 250, 202, 96, 39, 52, 1, 25, 243, 119, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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