Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6fbc769d382cc7f07bb1c88897abae344d6246ad2bafa4e8f96319f6d6e70c

Tx prefix hash: d4237fe8b8b9d65f75b9faae6cabfc7e1ae8114f75b5c9ef81d1b786b900e6e8
Tx public key: 6a408279a83320f28cf2ad537c879a75009d75918ce9aafa98749e67d04b812c
Timestamp: 1695477963 Timestamp [UCT]: 2023-09-23 14:06:03 Age [y:d:h:m:s]: 01:199:05:21:27
Block: 854454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403454 RingCT/type: yes/0
Extra: 016a408279a83320f28cf2ad537c879a75009d75918ce9aafa98749e67d04b812c021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.905397409000 dcy

stealth address amount amount idx
00: 58378caedd00c372070b9226fdb9c17da2897dbdb052b9581c69c2ee2ddc6b48 0.905397409000 1308428 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": 854464, "vin": [ { "gen": { "height": 854454 } } ], "vout": [ { "amount": 905397409, "target": { "key": "58378caedd00c372070b9226fdb9c17da2897dbdb052b9581c69c2ee2ddc6b48" } } ], "extra": [ 1, 106, 64, 130, 121, 168, 51, 32, 242, 140, 242, 173, 83, 124, 135, 154, 117, 0, 157, 117, 145, 140, 233, 170, 250, 152, 116, 158, 103, 208, 75, 129, 44, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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