Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d5b1644a53fcd525a06d6012d307f3cff7f23ee741e7968eb3eb4e7e8bce87f

Tx prefix hash: 63816523dcc036858a14f4dc76e9c0c3b6427b57f77a74c61f70c97f46b2de26
Tx public key: 07f2f55187956de0212ba8f217542a7219e88439f43d210d13317b81791cad98
Timestamp: 1698076832 Timestamp [UCT]: 2023-10-23 16:00:32 Age [y:d:h:m:s]: 01:190:09:13:08
Block: 876003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397095 RingCT/type: yes/0
Extra: 0107f2f55187956de0212ba8f217542a7219e88439f43d210d13317b81791cad98021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.768136555000 dcy

stealth address amount amount idx
00: 68bbd7738133ae434e11a4056ae7a3bc2b921cf58a97c03f4f925ed399acbbee 0.768136555000 1331311 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": 876013, "vin": [ { "gen": { "height": 876003 } } ], "vout": [ { "amount": 768136555, "target": { "key": "68bbd7738133ae434e11a4056ae7a3bc2b921cf58a97c03f4f925ed399acbbee" } } ], "extra": [ 1, 7, 242, 245, 81, 135, 149, 109, 224, 33, 43, 168, 242, 23, 84, 42, 114, 25, 232, 132, 57, 244, 61, 33, 13, 19, 49, 123, 129, 121, 28, 173, 152, 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